System and method for performing multistream storage operations

ABSTRACT

Systems and methods for performing storage operations over multi-stream data paths are provided. A first agent receives a request for a storage operation from a storage manager, identifies folders of a client computing device based on one or more file types of files in the folders of the client computing device, weights the folders based on the amount of data in the folders, and groups the folders into two or more sets of folders based at least in part on a file type of one or more of the files in the folders and the weight of the folders. A second agent transmits data from each of the two or more sets of folders to one or more storage devices in via at least one of two or more streaming communications paths based on pathway characteristics.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No. 13/168,748, entitled SYSTEM AND METHOD FOR PERFORMING MULTISTREAM STORAGE OPERATIONS, filed Jun. 24, 2011, which is a continuation of U.S. Pat. No. 7,975,061, entitled SYSTEM AND METHOD FOR PERFORMING MULTISTREAM STORAGE OPERATIONS, filed Nov. 7, 2005, which claims the benefit of U.S. provisional application No. 60/626,076 titled SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 8, 2004, and U.S. provisional application No. 60/625,746 titled STORAGE MANAGEMENT SYSTEM filed Nov. 5, 2004, each of which is incorporated herein by reference in its entirety.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to the following patents and pending applications, each of which is hereby incorporated herein by reference in its entirety:

U.S. Pat. No. 7,395,282, titled HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM, issued Jul. 1, 2008;

U.S. Pat. No. 6,418,478, titled PIPELINED HIGH SPEED DATA TRANSFER MECHANISM, issued Jul. 9, 2002;

Application Ser. No. 60/460,234, SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Apr. 3, 2003;

Application Ser. No. 60/482,305, HIERARCHICAL SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Jun. 25, 2003;

Application Ser. No. 60/519,526, SYSTEM AND METHOD FOR PERFORMING PIPELINED STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 13, 2003;

Application Ser. No. 10/803,542, METHOD AND SYSTEM FOR TRANSFERRING DATA IN A STORAGE OPERATION, filed Mar. 18, 2004;

Application Ser. No. 11/269,512, titled SYSTEM AND METHOD TO SUPPORT SINGLE INSTANCE STORAGE OPERATIONS, filed Nov. 7,2005;

U.S. Pat. No. 7,809,914, titled METHOD AND SYSTEM OF POOLING STORAGE DEVICES, issued Oct. 5, 2010;

U.S. Pat. No. 7,765,369, titled METHOD AND SYSTEM FOR SELECTIVELY DELETING STORED DATA, issued Jul. 27, 2010;

U.S. Pat. No. 7,500,053, titled METHOD AND SYSTEM FOR GROUPING STORAGE SYSTEM COMPONENTS, issued Mar. 3, 2009;

U.S. Pat. No. 7,472,238, titled SYSTEMS AND METHODS FOR RECOVERING ELECTRONIC INFORMATION FROM A STORAGE MEDIUM, issued Dec. 30, 2008; and

Application Ser. No. 11/269,513, titled METHOD AND SYSTEM FOR MONITORING A STORAGE NETWORK, filed Nov. 7, 2005.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

The invention disclosed herein relates generally to performing storage operations in a computer network. More particularly, the present invention relates to performing multiple stream storage operations from one or more subclients in a computer network.

Storage of electronic data has evolved through many forms. During the early development of the computer, storage of data was limited to individual computers. Electronic data was stored in the Random Access Memory (RAM) or some other storage medium such as a hard drive or tape drive that was an actual part of the individual computer.

Later, with the advent of networked computing, storage of electronic data gradually migrated from the individual computer to stand-alone storage devices and other storage devices accessible via a network, for example a tape library accessible via a network server or other computing device. These network storage devices soon evolved in the form of networked tape drives, libraries, optical libraries, Redundant Arrays of Inexpensive Disks (RAID), CD-ROM jukeboxes, and other devices. System administrators often use network storage devices to perform storage operations and make backup copies and other copies of data stored on individual client computers in order to preserve data against accidental loss, corruption, physical damage, and other risks.

Storage systems evolved to handle increasingly complex storage operations and increasingly large volumes of data. For example, some storage management systems began organizing system components and system resources into logical groupings and hierarchies such as storage operation cells of the CommVault QiNetix storage management system, available from CommVault Systems, Inc. of Oceanport, N.J., and as further described as further described in Application Ser. No. 60/482,305 and application Ser. No. 09/354,058 which are hereby incorporated by reference in their entirety.

In addition, other systems and methods were adopted to address performance and data transfer bottlenecks and other issues. For example, the data stream between a volume on which a storage operation, such as a backup operation, was to be performed and the intended destination for the storage operation copy of the data often presented a bottleneck and could only stream a specified amount of data at any given time. To address this issue, client volumes to be backed up, such as primary volumes, were logically subdivided and organized into portions of data, for example sub-clients as used in the QiNetix storage management system or other portions of data known in the art. Sub-clients typically represent static associations of portions of data of a volume and are mutually exclusive. Thus, a portion of data is given a label and the association is stored as a static entity in an index or other storage location used by the system. Sub-clients are also used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, etc. For example, an administrator might find it preferable to separate e-mail data from financial data using two different sub-clients having different storage preferences, retention criteria, etc.

Each individual sub-client was thereby allocated an individual data stream for performing storage operation thus increasing performance of storage operations for the entire volume. For example, if a volume was divided into four sub-clients, the volume could then be allocated four streams instead of one stream representing a theoretical fourfold increase in performance.

Despite these improvements, data from a single sub-client could only be transferred by a single stream and data transfer is still fundamentally atomic at the sub-client level. In some instances, for example, in enterprise class storage management systems storing terabytes or even megabytes of data, sub-clients are often extremely large and thus dividing a volume into additional sub-clients presented little performance advantage since the amount of data in each sub-client was still enormous.

SUMMARY OF THE INVENTION

The system of the present invention may receive a request to perform a storage operation may determine whether multi-streaming resources are available to perform a multi-stream storage operation. Availability of multi-streaming resources may be related to network pathways capable of supporting multi-stream storage operations (for example due to bandwidth capacity, cabling topologies, or other factors), existing network load related to other storage operations being or to be performed (e.g., determining whether or not a performing a multi-stream storage operation would exceed a specified network load threshold), availability of components capable of supporting multi-stream storage operation (i.e., containing appropriate software modules, hardware, etc.), and other factors. If the check fails, or system resources to support multi-stream storage operations are otherwise not available, then the system may perform a traditional storage operation that does not incorporate multiple streams as known in the art.

Otherwise, the system may automatically identify and analyze characteristics of the portion of a sub-client on which the storage operation is to be performed. The system may analyze characteristics of the sub-.client and other aspects of the storage management system as further described herein, and may use the information gathered to intelligently and dynamically create various logical subsets of the portion of data. These subsets are typically mutually exclusive and the storage operation is thus typically performed using multiple streams with a single stream directed to each individual subset of the portion of data resulting in parallelism and increased efficiency.

In some embodiments, a client data agent or other software module analyzes sub-client characteristics and other characteristics or aspects of the storage management system disclosed herein. This analysis may be performed by one or more stream managers associated with one or more media management components. In some embodiments, this analysis may be collaboratively performed by client data agents and one or more media management components or other system components such as storage management components, etc.

In some embodiments, the storage system may determine characteristics to analyze according to information stored in a storage management component index or other storage location or database. In other embodiments, the system determines characteristics to analyze according to a user preference or as manually directed or otherwise specified by a system administrator (e.g., according to default, optimized or specific selections actually made or approved by an administrator).

In some embodiments, the system may analyze sub-client characteristics according to data or sub-client size. According to one embodiment, a sub-client may be divided linearly according to the number of items. For example, a sub-client may be divided at the folder level such that an individual stream is allocated to each individual folder (or parsed into subsets of similar or equal size, depending on certain factors, for example, such as bandwidth of any associated streaming resources, required transfer time, etc.). Alternatively, a sub-client may be divided linearly among a particular number of streams. Thus, if a sub-client contains twenty folders, items, etc. and four streams have been designated for use in performing the storage operation, the system may divide the twenty items into four groups containing five items each with an individual stream used to perform the storage operation for each group.

In some embodiments, the system may also analyze and weight sub-client characteristics according to size in a non-linear manner. In some embodiments, the system may analyze sub-client characteristics according to file type. For example, it may be more suitable or efficient to process and perform certain types of storage operations on certain types of files. Thus, the system may divide a sub-client into groups according to file-type.

In some embodiments, the storage system may also identify and analyze storage network characteristics to determine how to divide sub-clients. For example, the system may analyze characteristics of the storage network such as network pathways to determine desirable pathways for various streams. The system may consider, for example, the impact of scheduled storage operations that would occur on various network pathways at the same or overlapping times as the requested storage operation to evaluate network load or other considerations such as to maintain bandwidth, throughput, etc. within various constraints or as specified by one or more thresholds. In some embodiments, the storage system may also identify and analyze storage network resources to determine how to divide sub-clients. For example, the system may evaluate the availability of one or more storage devices for performing the requested storage operation.

In some embodiments, the storage system may identify and analyze storage network resources and support sub-client multi-streaming across a plurality of storage operation cells. For example, components in a first storage operation cell may communicate with a master storage management component or other component regarding availability of transmission and storage resources in other storage operation cells. Assuming additional resources are available in other storage operation cells, the storage system may perform storage operations using multiple streams that span across multiple storage operation cells using resources in those other storage cells as further described herein.

Thus, the storage system of the present invention may identify and analyzes the various sub-client, storage network, and network resource characteristics according to various embodiments and determines the various sub-client subsets.

In operation, the storage system may create multiple streams and allocate a stream to each subset of data to perform the requested storage operation. The system may also update one or more indices with metadata and other information associated with the storage operation. For example, metadata generated and other information is generally stored in the index of the media management component responsible for processing the stream. Thus, if a single media management component processes streams for a given storage operation, the metadata generated by the storage operation may generally be stored in the index of that media management component as further described herein. The index of the storage management component associated with directing the storage operation is also generally updated indicating which media management component is responsible for the data, what data was stored, etc.

In some embodiments, however, multiple media management components may process a plurality of streams for a single sub-client storage operation, for example to load-balance a multi-stream storage operation, to perform a multi-stream storage operation across multiple storage operation cells, etc. In some embodiments, this index information may be copied to some or all media management component indices having responsibility for the storage operation. For example, if three media management components each processed one or more streams associated with a sub-client storage operation, the streaming manager or other component of a particular media management component may communicate the index information of that media management component to the other two media management components so that each (or some) of the three media management component have a complete index tracking the association of the streams of data stored on various storage devices throughout the storage management system. Alternatively, in some embodiments, once the storage operation is complete, the streaming manager or other component of two of the media management components may communicate their index information to the third media management component (thus creating a single complete copy of the metadata and other information at the third media management component) and delete or make available for overwrite their own index information, for example, to optimize index space utilized across the system. In some embodiments, a storage management component may communicate with media management components regarding the identity, address, or other identifier of other media management components in the system.

For example, if a streaming manager at a first media management component determines that insufficient resources exist (under the control of that media management component) to perform some or all of a particular storage operation, other resources may be sought to complete the contemplated operation. For example, the streaming manager may communicate this information to (e.g., as a request to other management components) and receive in return an responses indicating available resources and may include identifier information associated with another media management component (in the same or other storage operation cell) able to handle all or part of the particular storage operation including any other information necessary to coordinate the storage operation such as security or other access protocol information, firewall-related information (ports, passwords, certificates, identifiers, etc.), network pathways or other network-related information, storage device information, client information, etc. Thus, while various subsets of data may be stored on a plurality of storage devices across one or more storage operation cells, the data is easily tracked and accessible using media management component indices or other indices (such as storage manager indices in some embodiments).

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like references are intended to refer to like or corresponding parts, and in which:

FIG. 1 is a block diagram of a storage operation cell in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;

FIG. 2 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;

FIG. 3 is a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention;

FIG. 4 is a block diagram of a client data store in a system to perform storage operations on electronic data according to an embodiment of the invention;

FIG. 5 is a flow diagram of a method for performing multi-stream storage operations on electronic data according to an embodiment of the invention;

FIG. 6 is a block diagram of a storage operation cell performing multi-stream storage operations on electronic data according to an embodiment of the invention; and

FIG. 7 is block diagram of a plurality of storage operation cells performing multi-stream storage operations on electronic data according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference to FIGS. 1 through 7, embodiments of the invention are presented. Systems and methods are presented for performing multi-stream storage operations including multi-stream storage operations associated with a single sub-client.

FIG. 1 presents a block diagram of a storage operation cell in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the storage operation cell may include a storage management component, such as storage manager 100 and one or more of the following: a client 85, a data store 90, a data agent 95, a media management component, such as a media agent 125, a media management component index cache 130, a storage device 135, a storage management component index cache 105, a jobs agent 110, an interface module 115, and a management agent 120. The system and elements thereof are exemplary of a modular storage management system such as the Comm Vault QiNetix storage management system, available from Comm Vault Systems, Inc. of Oceanport, N.J., and further described in application Ser. No. 09/610,738 which is incorporated herein by reference in its entirety.

A storage operation cell generally includes combinations of hardware and software components directed to performing storage operations on electronic data. Exemplary storage operation cells according to embodiments of the invention include CommCells as embodied in the QNet storage management system and the QiNetix storage management system by CommVault Systems of Oceanport, N.J., and as further described in Application Ser. No. 60/482,305 and application Ser. No. 09/354,058 which are hereby incorporated by reference in their entirety.

According to some embodiments of the invention, storage operations cells are related to backup cells and provide all of the functionality of backup cells as further described in application Ser. No. 09/354,058. Storage operation cells also perform additional types of storage operations and provide other types of storage management functionality. According to embodiments of the invention, storage operation cells perform storage operations which also include, but are not limited to, creation, storage, retrieval, migration, deletion, and tracking of primary or production volume data, secondary volume data, primary copies, secondary copies, auxiliary copies, snapshot copies, backup copies, incremental copies, differential copies, HSM copies, archive copies, Information Lifecycle Management (“ILM”) copies, and other types of copies and versions of electronic data. In some embodiments, storage operation cells also provide an integrated management console for users or system processes to interface with to perform storage operations on electronic data as further described herein.

A storage operation cell can be organized and associated with other storage operation cells forming a logical hierarchy among various components of a storage management system as further described herein. Storage operation cells generally include a storage manager 100, and, according to some embodiments, one or more other components including, but not limited to, a client computer 85, a data agent 95, a media management component 125, a storage device 135.

For example, a storage operation cell may contain a data agent 95 which is generally a software module that is generally responsible for performing storage operations related to client computer 85 data stored in an data store 90 or other memory location, for example archiving, migrating, and recovering client computer data. In some embodiments, a data agent performs storage operations in accordance with one or more storage policies or other preferences. A storage policy is generally a data structure or other information that may include a set of preferences and other storage criteria for performing a storage operation. The preferences and storage criteria may include, but are not limited to: a storage location, relationships between system components, network pathway to utilize, retention policies, data characteristics, compression or encryption requirements, preferred system components to utilize in a storage operation, and other criteria relating to a storage operation. As further described herein, storage policies may be stored to a storage manager index, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.

Each client computer 85 generally has at least one data agent 95 and the system can support many client computers 85. The system also generally provides a plurality of data agents 95 each of which is intended to perform storage operations related to data associated with a different application, for example to backup, migrate, and recover application specific data. For example, different individual data agents 95 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows 2000 file system data, Microsoft Active Directory Objects data, and other types of data known in the art.

If a client computer 85 has two or more types of data, one data agent 95 is generally required for each data type to perform storage operations related to client computer 85 data. For example, to backup, migrate, and restore all of the data on a Microsoft Exchange 2000 server, the client computer 85 would use one Microsoft Exchange 2000 Mailbox data agent 95 to backup the Exchange 2000 mailboxes, one Microsoft Exchange 2000 Database data agent 95 to backup the Exchange 2000 databases, one Microsoft Exchange 2000 Public Folder data agent 95 to backup the Exchange 2000 Public Folders, and one Microsoft Windows 2000 File System data agent 95 to backup the client computer's 85 file system. These data agents 95 would be treated as four separate data agents 95 by the system even though they reside on the same client computer 85. In some embodiments, separate data agents may be combined to form a virtual data agent (not shown) for performing storage operations related to a specific application. Thus, the four separate data agents of the previous example could be combined as a virtual data agent suitable for performing storage operations related to all types of Microsoft Exchange 2000 and/or Windows 2000 data

The storage manager 100 is generally a software module or application that coordinates and controls storage operations performed by the storage operation cell. The storage manager 100 communicates with all elements of the storage operation cell including client computers 85, data agents 95, media management components 125, and storage devices 135 regarding storage operations, for example to initiate and manage system backups, migrations, and recoveries. The storage manager 100 also communicates with other storage operation cells as further described herein.

The storage manager 100 includes a jobs agent 110 software module which monitors the status of all storage operations that have been performed, that are being performed, or that are scheduled to be performed by the storage operation cell. The jobs agent 110 is communicatively coupled with an interface agent 115 software module. The interface agent 115 provides presentation logic, such as a graphical user interface (“GUI”), an application program interface (“API), or other interface by which users and system processes can retrieve information about the status of storage operations and issue instructions to the storage operations cell regarding performance of storage operations as further described herein. For example, a user might modify the schedule of a number of pending snapshot copies or other types of copies. As another example, a user might use the GUI to view the status of all storage operations currently pending in all storage operation cells or the status of particular components in a storage operation cell.

The storage manager 100 also includes a management agent 120 software module. The management agent 120 generally provides an interface with other management components 100 in other storage operations cells through which information and instructions regarding storage operations may be conveyed. For example, in some embodiments as further described herein, a management agent 120 in first storage operation cell can communicate with a management agent 120 in a second storage operation cell regarding the status of storage operations in the second storage operation cell. In some embodiments, ‘fl management agent 120 in first storage operation cell can communicate with a management agent 120 in a second storage operation cell to control the storage manager 100 (and other components) of the second storage operation cell via the management agent 120 contained in the storage manager 100 for the second storage operation cell. In other embodiments, the management agent 120 in the first storage operation cell communicates directly with and controls the components in the second storage management cell and bypasses the storage manager 100 in the second storage management cell. Storage operation cells can thus be organized hierarchically among cells and as further described herein.

A media management component 125 is generally a software module that conducts data, as directed by a storage manager 100, between client computers 85 and one or more storage devices 135. The media management component 125 is communicatively coupled with and generally configured to control one or more storage devices 135. For example, the media management component 125 might instruct a storage device 135 to use a robotic arm or other means to load or eject a media cartridge, and to archive, migrate, or restore application specific data. The media management component 125 generally communicates with storage devices 135 via a local bus such as a SCSI adaptor. In some embodiments, the storage device 135 is communicatively coupled to the media management component 125 via a Storage Area Network (“SAN”).

Each media management component 125 maintains an index cache 130 which stores index data the system generates during storage operations as further described herein. For example, storage operations for Microsoft Exchange data generate index data. Index data may include, for example, information regarding the location of the stored data on a particular media, information regarding the content of the data stored such as file names, sizes, creation dates, formats, application types, and other file-related criteria, information regarding one or more clients associated with the data stored, information regarding one or more storage policies, storage criteria, or storage preferences associated with the data stored, compression information, retention-related information, encryption-related information, stream-related information, and other types of information. Index data thus provides the system with an efficient mechanism for performing storage operations including locating user files for recovery operations and for managing and tracking stored data. The system generally maintains two copies of the index data regarding particular stored data. A first copy is generally stored with the data copied to a storage device 135. Thus, a tape may contain the stored data as well as index information related to the stored data. In the event of a system restore, the index data stored with the stored data can be used to rebuild a media management component index 130 or other index useful in performing and/or managing storage operations. In addition, the media management component 125 that controls the storage operation also may generally write an additional copy of the index data to its index cache 130. The data in the media management component index cache 130 is generally stored on faster media, such as magnetic media, and is thus readily available to the system for use in storage operations and other activities without having to be first retrieved from the storage device 135.

The storage manager 100 may also maintain an index cache 105. Storage manager index data may be, among other things, used to indicate, track, and associate logical relationships and associations between components of the system, user preferences, management tasks, and other useful data. For example, the storage manager 100 might use its index cache 105 to track logical associations between media management components 125 and storage devices 135. The storage manager 100 may also use index cache 105 to track the status of storage operations to be performed, storage patterns associated with the system components such as media use, storage growth, network bandwidth, service level agreement (“SLA”) compliance levels, data protection levels, storage policy information, storage criteria associated with user preferences, retention criteria, storage operation preferences, and other storage-related information. Index caches 105 and 130 typically reside on their corresponding storage component's hard disk or other fixed storage device.

For example, jobs agent 110 of a storage manager component 100 may retrieve storage manager index 105 data regarding a storage policy and storage operation to be performed or scheduled for a particular client 85. The jobs agent 110, either directly or via the interface module 115, communicates with the data agent 95 at the client 85 regarding the storage operation. In some embodiments, the jobs agent 110 also retrieves from index cache 105 a storage policy associated with client 85 and uses information from the storage policy to communicate to data agent 95 one or more media management components 125 associated with performing storage operations for that particular client 85 as well as other information regarding the storage operation to be performed such as retention criteria, encryption criteria, streaming criteria, etc. Data agent may 95 then package or otherwise manipulate client data stored in client data store 90 in accordance with the storage policy information and/or according to a user preference, and may communicate this client data to the appropriate media management component(s) 125 for processing. Media management component(s) 125 may store the data according to storage preferences associated with the storage policy including storing the generated index data with the stored data, as well as storing a copy of the generated index data in the media management component index cache 130.

In some embodiments, components of the system may reside and execute on the same computer. In some embodiments, a client computer 85 component such as a data agent 95, a media management component 125, or a storage manager 100 coordinates and directs storage operations as further described in application Ser. No. 09/610,738. This client computer 85 component can function independently or together with other similar client computer 85 components.

FIG. 2 presents a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, the system may include a master storage manager component 140, a first storage operation cell 145, a second storage operation cell 150, a third storage operation cell 155, a fourth storage operation cell 160, a fifth storage operation cell 165, and an nth storage operation cell 170.

As previously described, storage operation cells are often communicatively coupled and hierarchically organized. For example, as shown in FIG. 2, a master storage manager 140 is associated with, communicates with, and directs storage operations for a first storage operation cell 145, a second storage operation cell 150, a third storage operation cell 155, a fourth storage operation cell 160, a fifth storage operation cell 165, and an nth storage operation cell 170. In some embodiments, the master storage manager 140 is not part of any particular storage operation cell. In other embodiments (not shown), the master storage manager 140 may itself be part of a storage operation cell.

Thus, the master storage manager 140 communicates with the manager agent of the storage manager of the first storage operation cell 145 (or directly with the other components of the first cell 145) regarding storage operations performed in the first storage operation cell 145. For example, in some embodiments, the master storage manager 140 instructs the first storage operation cell 145 how and when to perform storage operations including the type of operation to perform and the data on which to perform the operation.

In other embodiments, the master storage manager 140 tracks the status of its associated storage operation cells, such as the status of jobs, system components, system resources, and other items, by communicating with manager agents (or other components) in the respective storage operation cells. In other embodiments, the master storage manager 140 tracks the status of its associated storage operation cells by receiving periodic status updates from the manager agents (or other components) in the respective cells regarding jobs, system components, system resources, and other items. For example, in some embodiments, the master storage manager 140 uses methods to monitor network resources such as mapping network pathways and topologies to, among other things, physically monitor storage operations and suggest alternate routes for storing data as further described herein. The master storage manager 140 also uses methods to monitor primary and secondary storage trends, storage status, media usage, data protection levels, and other storage-related information as further described herein.

In some embodiments, the master storage manager 140 stores status information and other information regarding its associated storage operation cells and the system in an index cache or other data structure accessible to the master storage manager 140. In some embodiments, as further described herein, the presentation interface of the master storage manager 140 accesses this information to present users and system processes with information regarding the status of storage operations, storage operation cells, system components, and other information of the system.

Storage operation cells may thus be organized hierarchically. Consequently, storage operation cells may inherit properties from “parent” or hierarchically superior cells or be controlled by other storage operation cells in the hierarchy. Thus, in some embodiments as shown in FIG. 2, the second storage operation cell 150 controls or is otherwise superior to the third storage operation cell 155, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170. Similarly, the fourth storage operation cell 160 controls the fifth storage operation cell 165, and the nth storage operation cell 170.

Storage operation cells may also be organized hierarchically according to criteria such as function (e.g., superior or subordinate), geography, architectural considerations, or other factors useful in performing storage operations. For example, in one embodiment storage operation cells are organized according to types of storage operations: the first storage operation cell 145 may be directed to performing snapshot copies of primary copy data, and the second storage operation cell 150 may be directed to performing backup copies of primary copy data or other data. In another embodiment, the first storage operation cell 145 may represent a geographic segment of an enterprise, such as a Chicago office, and a second storage operation cell ISO represents a different geographic segment, such as a New York office. In this example, the second storage operation cell 150, the third storage operation cell 155, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170 could represent departments within the New York office. Alternatively, these storage operation cells could be further divided by function performing various types of copies for the New York office or load balancing storage operations for the New York office.

In some embodiments, hierarchical organization of storage operation cells may facilitate, among other things, system security and other considerations. For example, in some embodiments, only authorized users are allowed to access or control certain storage operation cells. For example, a network administrator for an enterprise might have access to all storage operation cells including the master storage manager 140. But a network administrator for only the New York office, according to a previous example, might only satisfy access criteria to have access to the second storage operation cell ISO, the third storage operation cell ISS, the fourth storage operation cell 160, the fifth storage operation cell 165, and the nth storage operation cell 170 which comprise the New York office storage management system.

In some embodiments, hierarchical organization of storage operation cells facilitates storage management planning and decision-making. For example, in some embodiments, a user of the master storage manager 140 can view the status of all jobs in the associated storage operation cells of the system as well as the status of each component in every storage operation cell of the system. The user can then plan and make decisions based on this global data. For example, the user can view high-level report of summary information regarding storage operations for the entire system, such as job completion status, component availability status, resource usage status (such as network pathways, etc.), and other information. The user can also drill down through menus or use other means to obtain more detailed information regarding a particular storage operation cell or group of storage operation cells.

In other embodiments, the master storage manager 140 may alert a user or system administrator when a particular resource is unavailable (e.g., temporary or permanent) or congested. A storage device may be full or require additional media. Alternatively, a storage manager in a particular storage operation cell may be unavailable due to hardware failure, software problems, or other reasons. In some embodiments, the master storage manager 140 (or another storage manager within the hierarchy of storage operation cells) may utilize the global data regarding its associated storage operation cells at its disposal to suggest solutions to such problems when they occur or even before they occur. For example, the master storage manager 140 might alert the user that a storage device in a particular storage operation cell was full or otherwise congested, and then suggest, based on job and data storage information contained in its index cache, an alternate storage device.

As another example, in some embodiments the master storage manager 140 (or other network storage manager) contains programming directed to analyzing the storage patterns and resources of its associated storage operation cells and which suggests optimal or alternate methods of performing storage operations. Thus, for example, the master storage manager 140 may analyze traffic patterns to determine that snapshot data should be sent via a different network segment or to a different storage operation cell or storage device. In some 22 embodiments, users can direct specific queries to the master storage manager 140 regarding predicting storage operations or regarding storage operation information.

FIG. 3 presents a block diagram of a hierarchically organized group of storage operation cells in a system to perform storage operations on electronic data in a computer network according to an embodiment of the invention. As shown, FIG. 3 includes a first storage operation cell 175, a second storage operation cell 180, a third storage operation cell 185, a client 190 in communication with a primary volume 195 storing production or other “live” data, a storage manager component 200 in communication with a storage manager index data store 205, a media management component 210 in communication with a media management component index 215 a secondary storage device or volume 220, and a master storage manager component 225 in communication with a master storage manager index data store 230.

According to an embodiment of the invention, the first storage operation cell 175 may be directed to a particular type storage operation, such as SRM storage operations. For example, the first storage operation cell 175 monitors and performs SRM-related calculations and operations associated with primary volume 195 data. Thus, the first storage operation cell 175 includes a client component 190 in communication with a primary volume 195 storing data. For example, the client 190 may be directed to using Exchange data, SQL data, Oracle data, or other types of production data used in business applications or other applications and stored in primary volume 195. Storage manager component 200 in cell 175 contains SRM modules or other logic directed to monitoring or otherwise interacting with attributes, characteristics, metrics, and other information associated with the data stored in primary volume 195. Storage manager 200 tracks and stores this information and other information in storage manager index 205. For example, in some embodiments, storage manager component 200 tracks the amount of available space and other similar characteristics of data associated with primary volume 195. In some embodiments, as further described herein, storage manager component 200 may also issue alerts or take other actions when the information associated with primary volume 195 satisfies certain criteria, such as alert criteria.

The second storage operation cell 180 may be directed to another type storage operation, such as RSM storage operations. For example, the second storage operation cell 180 may perform backups, migrations, snapshots, or other types of HSM-related operations known in the art. For example, in some embodiments, data is migrated from faster and more expensive storage such as magnetic storage to less expensive storage such as tape storage.

In some embodiments, storage operation cells may also contain logical groupings of the same physical devices. Thus, the second storage operation cell 180 includes the client component 190 in communication with the primary volume 195 storing data, and client component 190 and primary volume 195 in the second storage operation cell 180 are the same physical devices as the client component 190 and primary volume 195 in the first storage operation cell 175. Similarly, in some embodiments, the storage manager component 200 and index 205 in the second storage operation cell 180 are the same physical devices as the storage manager component and index in the first storage operation cell 175. The storage manager component 200, however, also contains HSM modules or other logic associated with the second storage operation cell 180 directed to performing HSM storage operations on primary volume 195 data.

The second storage operation cell 180 therefore also contains a media management component 210, a media management component index 215, and a secondary storage volume 220 directed to performing HSM-related operations on primary copy data. For example, storage manager 200 migrates primary copy data from primary volume 195 to secondary volume 220 using media management component 210. Storage manager 200 also tracks and stores information associated with primary copy migration and other similar HSM-related operations in storage manager index 205. For example, in some embodiments, storage manager component 200 directs HSM storage operations on primary copy data according to according to a storage policy associated with the primary copy 195 and stored in the index 205. In some embodiments, storage manager 200 also tracks where primary copy information is stored, for example in secondary storage 220.

The third storage operation cell 185 contains a master storage manager 225 and a master storage manager index 230. In some embodiments (not shown), additional storage operation cells might be hierarchically located between the third storage operation cell 185 and the first storage operation cell 175 or the second storage operation cell 180. In some embodiments, additional storage operation cells hierarchically superior to the third storage operation cell 185 may also be present in the hierarchy of storage operation cells.

In some embodiments, the third storage operation cell 185 is also generally directed to performing a type of storage operation, such as integration of SRM and HSM data from other storage operation cells, such as the first storage operation cell 175 and the second storage operation cell 180. In other embodiments, the third storage operation cell 185 also performs other types of storage operations and might also be directed to HSM, SRM, or other types of storage operations. In some embodiments, the master storage manager 225 of the third storage operation cell 185 aggregates and processes network and storage-related data provided by other manager components 200 in other storage operation cells 175 and 180 in order to provide, among other information, reporting information regarding particular cells, groups of cell, or the system as a whole.

FIG. 4 presents a generalized block diagram of a client data store 235 in a system that performs storage operations on electronic data according to an embodiment of the invention. Data stores may include one or more hard disks or other suitable storage devices known in the art capable of storing electronic data logically organized into portions of data such as one or more volumes and/or sub-clients. As shown, client data store 235 may include hard disks HD 1 240, and HD2 245, and an nth hard disk HD3 250. Hard disk 240 is logically divided into a number of volumes and sub-clients including volume C: 255, all of which is included in sub-client SCI 265, and volume D: 260, the entirety of which is divided into two portions of data represented by sub-client SC2 270 and sub-client SC3 275. Hard disk 245 contains a volume E: 280, the entirety of which is divided into two portions of data represented by subclient SC4 285 and sub-client SC5 290. An nth hard disk, depicted as HD3 250, stores its electronic data on a volume F: 295, all of which is included in sub-client SC3 300.

FIG. 5 presents a flow diagram of a method for performing multi-stream storage operations on electronic data according to an embodiment of the invention. The system receives or otherwise generates as described herein a request to perform a storage operation at step 305. For example, a storage management component may schedule or otherwise direct a client or other system component regarding performance of a storage operation, such as a storage operation associated with a storage policy stored in a storage management component index. Thus, a storage manager management agent may communicate storage policy information and other storage preferences with a client data agent regarding the storage operation, for example, identifying the electronic data and subclient storing the electronic data on which the storage operation should be performed, identifying one or more media management components for the storage operation, identifying one or more storage devices to used for the storage operation or indicating that the identified one or more media management components will identify one or more storage devices to be used for the storage operation, indicating whether the storage operation can be performed using multiple streams, describing how the electronic data should be stored, for example, as compressed or encrypted electronic data, indicating a specified time period to retain the electronic data on the storage device(s), etc.

Assuming the request to perform a storage operation does not prohibit a multi-stream storage operation, the system may determine whether multi-streaming resources are available to perform a multi-stream storage operation, step 310. Availability faulty-streaming resources may be related to network pathways capable of supporting multi-stream storage operations (e.g., due to bandwidth capacity, cabling topologies, available routing options, or other factors), existing and/or predicted network load related to other storage operations being or to be performed (e.g., determining whether or not a performing a multi-stream storage operation would exceed a specified network load threshold), availability of components capable of supporting multi-stream storage operation (i.e., containing appropriate software modules, hardware, etc.), and any other factors that contribute to transmission of data.

For example, a storage manager, a stream manager, or other system component may perform one or more a diagnostic or discovery tests or checks to determine that one or more network pathways used by a particular storage policy is capable of supporting multi-stream storage operations and that components used to perform the storage operation associated with the storage policy are capable of supporting, handling and processing multi-stream storage operations. If the test or check fails, or system resources to support multi-stream storage operations are otherwise not available or scheduled to be unavailable, the system may perform a traditional storage operation that does not incorporate multiple streams as known in the art, step 315.

In some embodiments, the test may be deemed “failed” if all the necessary resources to perform the multi-stream storage operation are unavailable (or scheduled to be unavailable). However, in other embodiments, the storage system may identify certain missing resources and identify other constraints (e.g., time or scheduling) and provide options for obtaining necessary resources or provide the user with option to proceed with operation even though the test has strictly “failed.” This may involve manual intervention or override and may be performed automatically in an emergency or priority situation. For example, a network load or time threshold may be exceeded based on the proposed storage operation, or an operation of less priority may be “bumped” or rescheduled, but the user may instruct the system to proceed anyway. Moreover, in an emergency situation, it may be desirable to attempt storage operations even if only a portion of data will likely be successfully copied.

Otherwise, the system may automatically identify and analyze characteristics of the portion of sub-client on which the storage operation is to be performed, step 320. One reason this offers a significant advantage over prior art is because the system of the present invention is able to perform a storage operation on single sub-client using multiple streams. The system may analyze characteristics of the sub-client and other aspects of the storage management system as further described herein, and may use the information gathered to intelligently and dynamically create various logical subsets of the portion of data. These subsets of the portion of data are typically mutually exclusive and the storage operation may thus be performed using multiple streams with a single stream directed to each individual subset of the portion of data resulting in parallelism and increased efficiency.

In some embodiments, a client data agent or other software module analyzes sub-client characteristics and other characteristics or aspects of the storage management system. In other embodiments, this analysis may be performed by one or more stream managers associated with one or more media management components. For example, stream managers associated with different media management components may communicate regarding characteristics of one or more sub-clients and/or characteristics or aspects of the storage management system. In some embodiments, this analysis is collaboratively performed by client data agents and one or more media management components or other system components such as storage management components, etc.

In some embodiments, the system of the present invention may determine characteristics to analyze according to information stored in a storage management component index or other storage location. For example, the system may contain a data structure or other information specifying a set of sub-client and storage management system characteristics to analyze. In other embodiments, the system determines characteristics to analyze according to a user preference or as manually directed or otherwise specified by a system administrator.

In other embodiments, the system analyzes sub-client characteristics according to size. A sub-client generally contains a plurality of items such as files, folders, or other organizational divisions. According to one embodiment, a sub-client may be divided linearly according to the number of items. For example, a sub-client may be divided at the folder level such that an individual stream is allocated to each individual folder. Alternatively, a sub-client may be divided linearly among a particular number of streams. Thus, if a sub-client contains twenty folders, items, etc. and four streams have been designated for use in performing the storage operation, the system may divide the twenty items into four groups containing five items each with an individual stream used to perform the storage operation for each group.

Sub-client items, however, may vary greatly in size. A sub-client with twelve folders may contain a single folder storing 50% of the data of the entire sub-client, and it may be inefficient to linearly divide the sub-client and allocate streams in such a scenario. Thus, the system may also analyze and employing a scaling factor to “weight” sub-client characteristics according to size in a non-linear manner. Using the previous example, if the system had only four streams available for use in performing a storage operation associated with the sub-client, the system may divide the single folder storing 50% of the sub-client data into two groups (for example into two groups of files by analyzing the contents of the folder at the file size to create two groups of relatively equal size) allocating an individual stream for each group, and divide the remaining six folders into two groups of three folders each with an individual stream used to perform the storage operation for each group.

In some embodiments, the system analyzes sub-client characteristics according to file type. For example, it may be more suitable or efficient to process and perform certain types of storage operations on certain types of files. Thus, the system may divide a subclient into groups according to file-type. For example, a storage operation could take twice as long to perform for a first file type than for a second file type. If a sub-client contained twelve folders, with six folders storing data of the first file type and six folders storing an equal amount of data of the second file type, the system might allocate three streams to the sub-client by dividing the first six folders storing data of the first file type into two groups of three folders each with an individual stream allocated to each group, and associating the remaining six folders into a third group with an individual stream allocated to the third group. Thus, the storage operation for the sub-client would finish at approximately the same time for all streams.

In some embodiments, the system also identifies and analyzes storage network characteristics, step 325, to determine how to divide sub-clients. For example, the system may analyze characteristics of the storage network such as network pathways to determine desirable pathways for various streams. The system may consider, for example, the impact of scheduled storage operations that would occur on various network pathways at the same time as the requested storage operation of step 305 to evaluate network load or other considerations in order to maintain bandwidth, etc. within various constraints or a specified threshold.

Other considerations may include analyzing bandwidth of the transmission paths. If, for example, three streaming paths are available, one of which has twice the bandwidth of the other two, a sub-client may be divided correspondingly (e.g., into three parts, one part which may be twice the size of the other two) such that data is transferred form the sub-client to the destination storage device over substantially the same time period. In other embodiments, data may be divided according to priority, with more sensitive data being divided from less important data in the sub-client, with the sensitive data being assigned priority in order of transfer, bandwidth, security, etc., irrespective of size.

In some embodiments, the system also identifies and analyzes storage network resources, step 330, to determine how to divide sub-clients. For example, the system may evaluate the availability of one or more storage devices for performing the requested storage operation of step 305. It would be inefficient to allocate more streams to a sub-client storage operation than available storage device resources could support at a given time.

In some embodiments, the system may identify and analyze storage network resources that supports sub-client multi-streaming across a plurality of storage operation cells. For example, the system may determine that resources in a first cell only support a certain number of streams, (for example due to concurrent usage by other storage operations, device failures/unavailability, media space, etc.) that is less than a specified or desirable number of streams for the requested storage operation of step 305. Thus, components in the first storage operation cell may communicate with a master storage management component or other component regarding availability of storage resources in additional storage operation cells. Assuming additional resources were available in other storage operation cells, the system may perform the requested storage operation of step 305 using multiple streams across multiple storage operation cells as further described herein.

Thus, as can be seen from the above, the system identifies and analyzes the various sub-client, storage network, and network resource characteristics according to various embodiments and determines the various sub-client subsets, step 335.

In operation, the system may create multiple streams and allocate a stream to each subset of data, step 340, and perform the requested storage operation, step 345. For example, the system may create an instance of a high speed data transfer mechanism supporting multiple streams such as a data pipe as further described in U.S. Pat. No. 6,418,478 to transfer the data chunk-by-chunk to the designated storage device(s). Chunks of data from each subset of data are encapsulated and streamed as payload along with tag header and footer metadata describing the contents of each chunk as further described in application Ser. No. 09/495,751, and in application Ser. No. 10/803,542.

For example, metadata may include information including the sub-client associated with the chunk of data, the relationship of the chunk of data to other chunks of data from the sub-client (for example the order in which the chunks should be arranged, etc.), the date and time the data was generated, retention criteria associated with the data, encryption criteria associated with the data (e.g., a public key associated with the data, etc.), application-specific criteria associated with the data, a list of files contained in the chunk of data, the identity of the storage device on which the data is stored, the location of the data on the storage device (for example a tape offset, a sector, etc.), and other information. This metadata is generally stored with the chunks at the storage device in order to facilitate restore operations, disaster recovery operations, and other storage operations.

The system may also update one or more indices with metadata and other information associated with the storage operation, step 350. For example, metadata generated and other information is generally stored in the index of the media management component responsible for processing the stream. Thus, if a single media management component processes all streams for a given storage operation, the metadata generated by the storage operation is generally stored in the index of that media management component as further described herein. The index of the storage management component associated with directing the storage operation is also generally updated indicating which media management component is responsible for the data, what data was stored, etc.

In some embodiments, however, multiple media management components may process a plurality of streams for a single sub-client storage operation, for example to load-balance a multi-stream storage operation, to perform a multi-stream storage operation across multiple storage operation cells, etc. In some embodiments, this index information may be copied to some or all media management component indices responsible for the storage operation. For example, if three media management components each processed one or more streams associated with a sub-client storage operation, the streaming manager or other component of a particular media management component may communicate the index information of that media management component to the other two media management components so that each of the three media management component could have a complete index tracking the association of all streams of data stored on various storage devices throughout the storage management system. Alternatively, in some embodiments, once the storage operation is complete, the streaming manager or other component of two of the media management components may communicate their index information to the third media management component (thus creating a single complete copy of the metadata and other information at the third media management component) and delete their own index information, for example in order to optimize index space utilized across the system. In some embodiments, a storage management component may communicate with media management components regarding the identity, address, or other identifier of other media management components in the system.

For example, if a streaming manager at a first media management component determined that insufficient resources existed under the control of that media management component to perform all or part of a particular storage operation, the streaming manager may communicate this information and receive in return an identifier associated with another media management component (in the same or another storage operation cell) able to handle all or part of the particular storage operation including any other information necessary to coordinate the storage operation such as security or other access protocol information, firewall-related information (ports, passwords, certificates, identifiers, etc.), network pathways or other network-related information, storage device information, client information, etc.

Thus, while various subsets of data may be stored on a plurality of storage devices across one or more storage operation cells, the data is easily tracked and accessible using media management component indices or other indices (such as storage manager indices in some embodiments).

FIG. 6 presents a block diagram of a storage operation cell performing multi-stream storage operations on electronic data according to an embodiment of the invention. As shown, the storage operation cell contains a number of components and may include a storage manager 415 containing a management agent 420 and a storage manager index 425, a client 355 containing a data agent 360, a client data store 365 including a hard disk HDI 370 logically divided into a volume C: 375 and a sub-client SC3 380, a media management component 400 including a stream manager 405 and a media management component index 410, a first storage device 430, and a second storage device 435, for example a first tape library and a second tape library.

The components may be configured to perform multi-stream storage operations from sub-client SC3 380. For example, the storage manager 415 may schedule or otherwise direct client 355 regarding performance of a storage operation, such as a storage operation associated with a storage policy stored in storage management component index 425. Thus, management agent 420 may communicate storage policy information and other storage preferences to data agent 360 regarding the storage operation, for example, identifying the electronic data on which the storage operation should be performed, indicating that sub-client SC3 380 contains such electronic data, identifying media agent 400 as the media management component for the storage operation, identifying the storage devices used for the storage operation, such as one or both of storage devices 430 and 435, indicating that the storage operation can be performed using multiple streams, describing how the electronic data should be stored, for example as compressed or encrypted electronic data, indicating that the electronic data should be retained for a specified time period, etc, Management agent 420 may also communicate storage policy information and other storage preferences to media management component 400, for example to stream manager 405.

For example, management agent 420 may direct data agent 360 to initiate a backup operation of data on sub-client SC3 380 to storage devices 430 and 435 using three streams via media management component 400. Data agent 360 or another system component may analyze characteristics of sub-client SC3 380 and other characteristics of the storage system to dynamically create three subsets of the data stored in subclient SC3 380. For example, data agent 360 analyzes the items in sub-client SC3 380 according to item size and type, and also analyzes the network pathways between the client 355 and the media management component 400, as well as between the client and the storage devices 430 and 435 as appropriate. In some embodiments, stream manager 405 may perform a portion of this analysis in communication with data agent 360. In some embodiments, stream manager 405 performs the sub-client and storage system analysis instead of data agent 360.

The sub-client SC3 380 may be divided into three subsets and a data pipe is opened allocating a stream 385, 390, and 395 to each subset. Chunks of data are encapsulated with metadata and sent via streams 385, 390, and 395 to media management component 400. Stream manager 405 or another component of media management component 400 may manage the transfer of data from the sub-client SC3 380 to the storage devices 430 and 435. For example, media management component 400 may determine that the streams should be spread across two storage devices due to considerations such as media availability, connection bandwidth, future storage operation requirements, etc. Thus, stream 390 is written to drive 440 and stream 395 is written to drive 450 in storage device 430, while stream 385 is written to drive 465 of storage device 435. Drives 445 and 455 of storage device 430, as well as drives 460, 470, and 475 of storage device 435, remain available for additional storage operations.

The system also updates the media management index 410 with the metadata and other information generated by each stream of data. Thus, media management index 410 may store associations between the various streams and their locations, on the storage devices, the association of the various streams with sub-client SC3 380, the time and date of the storage operation, and other information as further described herein.

FIG. 7 presents a block diagram of a plurality of storage operation cells performing multi-stream storage operations on electronic data according to an embodiment of the invention. As show, FIG. 7 may include a first storage operation cell 480 and a second storage operation cell 485 arranged in a hierarchy and in communication with a master storage manager 490. The storage operation cells 480 and 485 include several clients 495, 500, and 580 in communication with one or more storage management components 505 and 580, one or more client data stores 660,675, and 725, one or more media management components 510, 515, 590, and 595, and one or more storage devices 520, 540, 600, and 620.

The components are configured to perform multi-stream storage operations from sub-clients SCI 665, SC2 680, SC3 685, SC4 730 and SC5 735. For example, the storage manager 415 may schedule or otherwise direct client 495 regarding performance of a storage operation for sub-client SCI 665, and communicates storage policy information and other storage preferences to client 495 (for example to a data agent at client 495) regarding the storage operation. The system determines that the storage operation, for example a backup operation, will be performed using a single stream 670 to a drive 525 of storage device 520 and via media management component 510. In some embodiments, a single stream may be used due to a failure of a system check for multi-streaming resources, for example if client 495 does not support multi-streaming. Thus, data from sub-client 665 encapsulated and streamed along with metadata describing the data to the drive 525 in storage device 520. The system may also update the media management component index 560 with the metadata and other information generated by the storage operation as further described herein.

As another example, the storage manager 415 (or other system component, for example the master storage manager 490) may schedule or otherwise direct client 500 regarding performance of one or more storage operations for sub-client SC2 680, and communicates storage policy information and other storage preferences to client 500 regarding the storage operation. The system determines that the storage operation, for example a differential backup operation, will be performed using three streams via media management components 510 and 515 to drives 530 and 535 of storage device 520, as well as to drive 545 of storage device 540. Media management components 510 and 515 may both be used to perform load balancing for the storage operation or due to characteristics of the network as further described herein.

For example, the system may analyze network characteristics and discover that it is desirable to use both media management components due an ability to increase data throughput using a network pathway in communication with one of the two media management components 510 and 515. Thus, the system divides sub-client SC2 680 into three subsets according to, for example a weighted file size analysis or by file type, etc., initializes a data pipe between sub client SC2 680 and the storage devices 520 and 540, encapsulates the data of each subset along with related metadata, and streams the data chunk by chunk via streams 690, 695, and 700. The system also updates the media management component index 560 with the metadata and other information generated by the storage operation as further described herein. In some embodiments, media agent 510 communicates its index information to media agent 515 and media agent 5 I 5 communicates its index information to media agent 510 in order that each media agent may maintain a full copy of the index data regarding storage of the streams for sub-client SC2 680. In other embodiments, one of the media agents may communicate its index information regarding the storage operation to the other (thus giving the other media management component a full copy of the index data regarding storage of the streams for sub-client SC2 680) and then subsequently delete its own index information regarding the storage operation in order to conserve index space, etc. as further described herein.

As yet another example, the storage manager 415 (or other system component, for example the master storage manager 490) may schedule or otherwise direct client 500 regarding performance of one or more storage operations for sub-client SC3 685, and communicates storage policy information and other storage preferences to client 500 regarding the storage operation. The system determines that the storage operation, for example another backup operation, will be performed using three streams via media management component 515. While the data agent of client 500 and the stream manager 575 of media management component 515 are identifying and analyzing characteristics of the network and network resources, the system determines that only two drives, drive 550 and drive 555 of storage device 540, are available within the first storage operation cell 480 to perform the storage operation and that these drives will each only support a single stream of data during the storage operation. Thus, a third drive or other storage location is required if the system is to perform the storage operation with three streams as is desirable. As another example, the system might determine that additional resources are required if a storage device in a particular storage operation cell, such as storage device 540 were unavailable due to hardware failure, lack of available media space, network connectivity issues, or for other reasons.

In some embodiments, stream manager 575 communicates this information to storage management component 505 which in turn contacts master storage manager 490 regarding the availability and characteristics of additional resources to support the multi-streaming operation for sub-client SC3 685. Master storage manager 490 may conduct its own analysis of available network resources in other cells by consulting its own index (not shown), by communicating with other master storage managers in a hierarchy of master storage managers, by communicating with other storage management components in other cells, for example with storage manager 585 in the second storage operation cell 485, or other system components.

Master storage manager 490 thus determines that additional resources are available in the second storage operation cell 485 and communicates this information to stream manager 475 either directly, or via management component 505. For example, master storage manager 490 may communicate the network address or other identifier of media management component 590 or storage device 600 in the second storage operation cell, access protocols or other security-related information regarding performing storage operations to the second storage operation cell 485, firewall-related information as necessary, and other information required for performing storage operations between storage operation cells.

The system may dynamically divide sub-client SC3 into three subsets as further described herein and performs the storage operation via streams 705 and 710 to the drives 550 and 555 respectively of storage device 540. In some embodiments, sub-client SC3 685 communicates with stream manager 645 in the second storage operation cell via stream manager 575 in the first storage operation cell and performs the storage operation as shown with a third stream 715 to drive 605 of storage device 600 in the second storage operation cell 485. In other embodiments, sub-client SC3 685 communicates directly with stream manager 645 in the second storage operation cell and performs the storage operation as shown with a third stream 720 to media management component 590 and then to drive 605 of storage device 600 via the remaining leg of stream 715 between the media management component 590 and the storage device 600 in the second storage operation cell 485. Index data is updated as previously discussed with either stream manager 645 communicating its index information to stream manager 575 and stream manager 575 communicating its index information to stream manager 645 (either directly or via various management components 505 and 585 and/or master storage manager 490) in order to create two full copies of the index information regarding storage of the streams, or one of either stream manager 575 or stream manager 645 communicating its information to the other in order to create a single full copy of the index information regarding storage of the streams and deleting its own index information regarding only those streams handled by its particular media management component 5′15 or 590 respectively.

In addition to the storage operations being performed in the first storage operation cell 480, the second storage operation cell 485 is also configured to simultaneously perform additional multi-steam storage operations regarding its own sub-clients, for example for sub-clients SC4 730 and SC5 735. Thus, the system also performs storage operations for sub-clients SC4 730 and SC5 735 by dividing the sub-clients into subsets for streaming as required and as previously discussed, and streaming data via streams 740, 745, and 750 to drives 610, 625, and 635 respectively of storage device 600 and storage device 620.

Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, hardware, or other means suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser or other application in an ASP context, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes, methods, or means, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, physical interfaces, and other interfaces suitable for the purposes described herein. Screenshots presented and described herein can be displayed differently as known in the art to generally input, access, change, manipulate, modify, alter, and work with information.

While the invention has been described and illustrated in connection with preferred embodiments, many variations and modifications as will be evident to those skilled in this art may be made without departing from the spirit and scope of the invention, and the invention is thus not to be limited to the precise details of methodology or construction set forth above as such variations and modification are intended to be included within the scope of the invention. 

1. A method for performing a dynamic multi-stream storage operation to transmit data from a client computing device to one or more storage devices, the method comprising: receiving a request for a storage operation from a storage manager; identifying folders of an information store associated with a client computing device based on one or more file types of files in the folders of the information store; weighting the folders using one or more processors based on the amount of data in the folders; grouping the folders into two or more sets of folders based at least in part on a file type of one or more of files in the folders and the weight of the folders; and transmitting data from each of the two or more sets of folders to one or more storage devices via at least one of two or more streaming communications paths based on pathway characteristics, wherein the pathway characteristics include a determination whether a transmission time threshold is exceeded by transmitting data over at least one of the two or more streaming communication paths.
 2. The method of claim 1, further comprising determining whether storage network resources within the two or more streaming communication paths are available.
 3. The method of claim 1, further comprising determining whether performing a multi-stream storage operation over only one streaming communication path would exceed a load threshold.
 4. The method of claim 1, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on a priority level of the folders.
 5. The method of claim 1, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on an impact of scheduled data transmissions.
 6. The method of claim 1, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on the number of items in the folders.
 7. The method of claim 1, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on available storage devices within the streaming communication paths.
 8. The method of claim 7, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on a capacity of the available storage devices.
 9. The method of claim 1, wherein grouping the folders into the two or more sets of folders further comprises grouping the folders based at least in part on a transmission time of data associated with the first sub-client.
 10. The method of claim 1, further comprising allocating each of the two or more sets of folders to a respective one of the two or more streaming communication paths dynamically based at least in part on a number of the sets of folders.
 11. The method of claim 1, wherein the each folder of the client is transmitted via a separate streaming communication path.
 12. The method of claim 1, further comprising allocating a first set of folders of the two or more sets of folders to a first streaming communication path based at least in part on the characteristics of the first streaming communication path and on the weight associated with the folders of the first set of folders.
 13. A multi-stream storage operation system comprising: a first agent, executing in one or more processors on a computing device and configured to: receive a request for a storage operation from a storage manager, identify folders of a client computing device based on one or more file types of files in the folders of the client computing device, weight the folders based on the amount of data in the folders, and group the folders into two or more sets of folders based at least in part on a file type of one or more of the files in the folders and the weight of the folders; and a second agent, executing in one or more processors on a computing device and configured to: transmit data from each of the two or more sets of folders to one or more storage devices via at least one of two or more streaming communications paths based on pathway characteristics, wherein the pathway characteristics include a determination whether a transmission time threshold is exceeded by transmitting data over at least one of the two or more streaming communication paths.
 14. The system of claim 13, wherein the first agent is a data agent and the computing device is the client computing device.
 15. The system of claim 13, wherein the first agent groups the folders based at least in part on a bandwidth of the storage network.
 16. The system of claim 13, wherein the first agent groups the folders based at least in part on an impact of scheduled data transmissions.
 17. The system of claim 13, wherein the first agent groups the folders based at least in part on an availability of the storage network resources.
 18. A computer-readable, non-transitory storage medium having one or more computer-executable modules for multi-stream storage operations, the one or more computer-executable modules comprising: a weighting module configured to: receive a request for a storage operation from a storage manager, identify folders of a client computing device based on one or more file types of files in the folders of the client computing device, weight the folders based on the amount of data in the folders, and group the folders into two or more sets of folders based at least in part on a file type of one or more of files in the folders and the weight of the folders; and a transmission module configured to: transmit data from each of the two or more sets of folders to one or more storage devices via at least one of two or more streaming communications paths based on pathway characteristics, wherein the pathway characteristics include a determination whether a transmission time threshold is exceeded by transmitting data over at least one of the two or more streaming communication paths.
 19. The computer-readable, non-transitory storage medium of claim 18, wherein the weighting module groups the folders based at least in part on an impact of scheduled data transmissions
 20. The computer-readable, non-transitory storage medium of claim 18, wherein the weighting module groups the folders based at least in part on the number of items in the folders. 